Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@src/app/globals.css`:
- Around line 179-185: Move the WebKit scrollbar pseudo-element rule inside the
Tailwind utility definition so all no-scrollbar styles are together: update the
`@utility` no-scrollbar block (the existing block containing -ms-overflow-style
and scrollbar-width) to also include the .no-scrollbar::-webkit-scrollbar rule
instead of having it defined separately; ensure the pseudo-element selector
(.no-scrollbar::-webkit-scrollbar) is nested/placed within the same `@utility`
no-scrollbar declaration so the WebKit rule is applied wherever the utility is
used.

In `@src/app/groups/create/page.tsx`:
- Around line 294-315: The textarea for clubDescription (the JSX element using
value={clubDescription}, onChange calling setClubDescription and autoResize) is
missing an enforced character limit; add a maxLength={500} attribute to that
textarea and ensure the onChange handler (setClubDescription) also
guards/truncates input to 500 chars. Do the same for the other field referenced
in the comment (the shorter text input around the second diff, e.g., the
title/input with 40자 제한) by adding maxLength={40} and enforcing/truncating in
its onChange handler so the UI constraint is actually applied.
- Around line 122-136: The refetch result from nameQuery.refetch() must be
validated because TanStack Query v5 returns a result object rather than
throwing; after calling nameQuery.refetch() check r.isError and ensure r.data is
a boolean before using it: if r.isError or typeof r.data !== "boolean"
setNameCheck("idle") and toast.error("이름 중복 확인 실패"); only when r.data ===
true/false proceed to setNameCheck("duplicate"/"available") and call the
corresponding toast; alternatively pass { throwOnError: true } to
nameQuery.refetch() and keep the existing try/catch but prefer explicit
r.isError/type guard for clarity.

In `@src/app/groups/page.tsx`:
- Around line 226-227: Change the catch clause to accept unknown instead of any
and narrow the error before using its message: replace the catch parameter in
the try/catch around the group join flow with (e: unknown), then check (e
instanceof Error) to call toast.error(e.message) and fall back to
toast.error("가입 신청에 실패했습니다.") for non-Error values; this uses the existing
toast.error call and matches the error-handling pattern in PasswordEntry.tsx and
useProfileImage.ts.
- Around line 231-246: The onSubmitSearch handler calls refetchSearch
immediately after setAppliedParams which causes a stale manual refetch; remove
the refetchSearch() call from onSubmitSearch and let React Query auto-refetch
based on the changed appliedParams (i.e., update only inside onSubmitSearch:
call setAppliedParams({...}) and return), or if you truly need an immediate
fetch, compute the new params into a local const and call refetchSearch with
those explicit params instead of relying on state.

In `@src/components/base-ui/BookStory/bookstory_card_large.tsx`:
- Around line 56-64: Replace the non-semantic, clickable divs that handle
profile and like actions with semantic <button type="button"> elements so they
are keyboard-focusable and actionable (preserve visual classes by moving
className to the button), keep the existing handlers (onProfileClick,
onLikeClick) but move e.stopPropagation() into the button onClick and remove any
manual onKey handlers; also add an appropriate aria-label for screen readers
(e.g., "Open profile" / "Like story") and ensure buttons do not submit forms by
specifying type="button". This change applies to the block using onProfileClick
and the analogous like-action block (the second clickable div).

In `@src/components/base-ui/BookStory/bookstory_card.tsx`:
- Around line 137-146: Replace the clickable div used for the like control with
a semantic button element (same place where onClick stops propagation and calls
onLikeClick, referencing onLikeClick, likedByMe and likeCount) for both mobile
and desktop footers; keep the existing classes but move them to a <button
type="button">, preserve e.stopPropagation() in the onClick handler, add an
accessible label/aria-pressed (e.g., aria-pressed={likedByMe}) and ensure the
Image and span remain inside the button so keyboard users and screen readers can
interact correctly.

In `@src/components/base-ui/BookStory/bookstory_detail.tsx`:
- Around line 189-197: Replace the clickable divs used for the like control with
semantic button elements to enable keyboard access and ARIA state; in the mobile
block (the element wrapping Image heartIcon and the span showing 좋아요
{likeCount}) and the tablet/desktop block do the following: change the outer
<div> to a <button>, keep the onClick handler (onLikeClick) and
e.stopPropagation logic, add type="button", add aria-pressed={likedByMe} and an
accessible aria-label (e.g., `aria-label={likedByMe ? '좋아요 취소' : '좋아요'}`),
preserve classes (cursor, hover, p-1, rounded-full, transition-colors) and the
conditional text color using likedByMe; ensure the Image and span remain
children and remove any duplicate keyboard/role workarounds so both likeCount
and toggle behavior remain unchanged.

In `@src/components/base-ui/Group-Search/search_club_apply_modal.tsx`:
- Around line 67-75: The modal container div (the element that builds className
via ["w-full max-w-[1040px]", "flex flex-col items-end gap-4", ...].join(" "))
must expose dialog semantics: add role="dialog" and aria-modal="true", and set
aria-labelledby to the id of the modal title (create an id like
"apply-modal-title" on the title/header element). Also add an optional
aria-describedby pointing to the element with the modal body or instructions if
present, and ensure the title element has that matching id; apply the same
changes to the other modal container instance noted in the file (around the
second occurrence at 88).

In `@src/components/base-ui/Profile/OtherUser/ProfileUserInfo.tsx`:
- Around line 117-118: The ProfileUserInfo component is rendering hardcoded
zeros via the StatItem calls; update ProfileUserInfo to not render those
StatItem elements until real values are available by conditionally rendering
them (e.g. render <StatItem label="구독 중" count={subscriptionCount} /> and
<StatItem label="구독자" count={subscriberCount} /> only when
subscriptionCount/subscriberCount are non-null/defined or the API call has
returned), or hide the whole stats block during loading; tie the checks to the
actual data source used in this component (e.g. props/state like
subscriptionCount, subscriberCount or the fetchUserStats/useUser hook) so dummy
0s are never shown.

In `@src/hooks/mutations/useMemberMutations.ts`:
- Line 186: Replace the explicit any types used for the onError callback
parameters with unknown in src/hooks/mutations/useMemberMutations.ts — update
the onError signatures (the callbacks currently declared as onError: (error:
any, variables, context) => { ... }) to use onError: (error: unknown, variables,
context) => { ... } for all three occurrences (the handlers around lines ~55,
~117, and ~186), and if the handler body uses the error value, narrow or
stringify it (e.g., String(error) or check typeof) before passing to
console.error or other APIs to satisfy TypeScript safety.
- Around line 127-135: The throttling check currently inside mutationFn (using
followThrottleMap and now/lastTime) causes onMutate to run for throttled calls
and produce optimistic updates; move that throttle logic out so the mutation
never starts when blocked: remove the early-return throttle from mutationFn and
instead perform the 500ms check in the caller/wrapper that invokes the mutation
(e.g., the function that calls followMutation.mutate or the exported
toggleFollow handler), using followThrottleMap[nickname] to gate calling
followMutation.mutate so onMutate/onSettled never run for throttled clicks.

In `@src/hooks/mutations/useStoryMutations.ts`:
- Around line 149-160: Move the throttle logic out of mutationFn into onMutate:
in onMutate check likeThrottleMap[bookStoryId] and if throttled set
likeThrottleMap and return a context object {throttled: true} so you can skip
optimistic updates in onMutate and have onSettled check context.throttled to
skip cache invalidation; also keep a guard at the top of mutationFn (still
referencing likeThrottleMap and storyService.toggleLikeStory) to early-return if
throttled to avoid making the API call; finally, include storyKeys.all in the
invalidation list used by onSettled (alongside infiniteList, myList, list,
detail) so otherMember caches are refreshed.
- Around line 171-190: The otherMember caches (storyKeys.otherMember(nickname))
are not updated when toggling likes; update them optimistically in onMutate and
invalidate them in onSettled similar to the infinite/my lists. In onMutate, if
previousOtherMember (or however you store the previous cache for otherMember)
exists call
queryClient.setQueryData<InfiniteData<BookStoryListResponse>>(storyKeys.otherMember(nickname),
old => updateLikeInInfiniteList(old, bookStoryId)) or
queryClient.setQueryData<BookStoryListResponse>(storyKeys.otherMember(nickname),
old => updateLikeInStoryList(old, bookStoryId)) to match the shape; in onSettled
call queryClient.invalidateQueries(storyKeys.otherMember(nickname)) to refetch.
Ensure you reference storyKeys.otherMember, updateLikeInInfiniteList,
updateLikeInStoryList, queryClient.setQueryData and
queryClient.invalidateQueries when applying the change.

In `@src/lib/api/types.ts`:
- Around line 1-7: Remove the duplicate ApiResponse type declaration in this
file and instead rely on the canonical ApiResponse<T = unknown> defined in
src/types/auth.ts; either delete the local export of ApiResponse or replace it
with an import and re-export (e.g., import { ApiResponse } from 'src/types/auth'
and export type { ApiResponse }), ensuring no duplicate type declarations remain
and that usages across authService and other services reference the single
canonical type.

In `@src/services/clubService.ts`:
- Line 35: Replace the explicit any on the sanitization object by typing it
instead of using any: change "const cleaned: any = { ...params }" to a typed
version such as "const cleaned: Partial<typeof params> = { ...params }" or, if
there is a declared request param interface (e.g. ListClubsParams or
ClubQueryParams), use that like "const cleaned: Partial<ListClubsParams> = {
...params }"; ensure you import/use the actual params type where available so
the linter rule `@typescript-eslint/no-explicit-any` is satisfied and type safety
is preserved when cleaning request parameters.

In `@src/services/imageService.ts`:
- Around line 43-45: Check that the presigned response is successful and
contains a result before destructuring; update the code that uses
presigned.result (the variable presigned and its properties presigned.result,
presignedUrl, imageUrl) to first assert presigned?.isSuccess is true and
presigned?.result exists, throw or return a descriptive error if not, and only
then call putToPresignedUrl(presignedUrl, file, contentType); this ensures you
don't destructure undefined and surfaces a clear error when the presign API
fails.

In `@src/services/memberService.ts`:
- Around line 37-42: The getOtherProfile function currently returns
response.result! without guarding for failure; update getOtherProfile in
memberService.ts to check the ApiResponse (e.g. response.isSuccess and that
response.result is defined) after awaiting
apiClient.get(MEMBER_ENDPOINTS.GET_OTHER_PROFILE(nickname)) and throw a
descriptive error (or reject) when isSuccess is false or result is missing
instead of using the non-null assertion on response.result; use the ApiResponse
type and MEMBER_ENDPOINTS.GET_OTHER_PROFILE reference to locate the code.

---

Outside diff comments:
In `@src/app/`(main)/page.tsx:
- Around line 106-124: The BookStoryCardLarge instances are rendering the
current likedByMe state but not wiring the like action, so clicks do nothing;
add an onLikeClick prop to each BookStoryCardLarge that invokes the existing
like handler (e.g., call toggleLike or the component's like handler used
elsewhere) with the story identity and current liked state (for example pass
story.bookStoryId and story.likedByMe or an object the handler expects). Update
the mappings that create BookStoryCardLarge (the shown block and the other two
similar mappings) to pass onLikeClick={() => toggleLike({ bookStoryId:
story.bookStoryId, liked: story.likedByMe })} (or the equivalent signature your
toggleLike accepts) so likes are dispatched when the user taps the like button.

In `@src/components/base-ui/Group-Search/search_mybookclub.tsx`:
- Around line 75-85: Replace the clickable div used in displayGroups.map (the
element with key={group.id} and onClick={() =>
router.push(`/groups/${group.id}`)}) with Next.js Link navigation: import Link
from 'next/link', use <Link href={`/groups/${group.id}`} ...> to preserve the
existing className, children (the span showing group.name) and key, and remove
the useRouter import and router variable if they are no longer used elsewhere;
this restores native link behavior (keyboard, context menu, new-tab) and fixes
the accessibility issues from using a div with onClick.

---

Nitpick comments:
In `@src/lib/api/endpoints/Image.ts`:
- Line 1: The import of API_BASE_URL in Image.ts currently comes from
"../endpoints" which diverges from sibling modules; update the import to use the
common source (import API_BASE_URL from "./base") so Image.ts uses the same base
URL provider as other endpoint modules—locate the import statement at the top of
Image.ts and replace the "../endpoints" module specifier with "./base" (keep the
API_BASE_URL identifier and any existing named/default import shape intact).

In `@src/lib/api/endpoints/index.ts`:
- Around line 6-7: The exports in index.ts use PascalCase ("./Clubs", "./Image")
which is inconsistent with the existing lowercase module names; rename the
module files Clubs.ts → clubs.ts and Image.ts → image.ts and update the exports
in src/lib/api/endpoints/index.ts to export * from "./clubs" and export * from
"./image" so the filenames and import/exports follow the lowercase convention
used by base, auth, bookstory, member, and book.

In `@src/types/groups/clubsearch.ts`:
- Line 1: The current import brings in ApiResponse as a value import even though
it is only used in type aliases; change the import to a type-only import so
TypeScript emits no value import (replace the existing import of ApiResponse
with a type-only import), updating the import statement that references
ApiResponse from "@/lib/api/types" and ensure all uses of ApiResponse remain as
type annotations only (e.g., in any type aliases or interfaces).

Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@src/hooks/mutations/useStoryMutations.ts`:
- Around line 155-167: Move the 500ms throttle check out of mutationFn and into
the very first lines of onMutate so clicks are short-circuited before any
optimistic update; use the existing likeThrottleMap and bookStoryId to compute
now/lastTime and, if throttled, return a context object like { throttled: true }
so the mutation lifecycle knows to skip further work. In addition, update
onError and onSettled to guard on context?.throttled and immediately return (no
rollback or invalidation) when true. Keep mutationFn calling
storyService.toggleLikeStory(bookStoryId) only for non-throttled cases. Ensure
the same pattern is applied for handlers referencing onError/onSettled to
prevent flicker/refetch.

---

Nitpick comments:
In `@src/hooks/mutations/useStoryMutations.ts`:
- Around line 54-55: The update that sets commentCount can go negative in
stale-cache edge cases; change the assignment in useStoryMutations that
currently does "commentCount: story.commentCount + delta" to clamp at zero
(e.g., use Math.max(0, story.commentCount + delta)) so commentCount never
becomes negative, and apply the same change to the second occurrence around
lines 72-73.